| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.2.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_2_Manage_Historical_Clinical_Data_and_Current_State_Data |
| Title | PH.2 Manage Historical Clinical Data and Current State Data (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Historical health information as well as current health status should be captured and maintained in the health record. |
| Purpose | To obtain historical information to populate the PHR, the PHR Account Holder may use strategies that include entering historical information directly or importing at least part of this data from outside electronic data sources. An outside service such as an employer, insurance plan, provider or care delivery organization may sponsor a particular PHR and add data to the record from their data sources. The PHR Account Holder may use similar strategies to populate their current state information. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Historical health information as well as current health status should be captured and maintained in the health record.
To obtain historical information to populate the PHR, the PHR Account Holder may use strategies that include entering historical information directly or importing at least part of this data from outside electronic data sources. An outside service such as an employer, insurance plan, provider or care delivery organization may sponsor a particular PHR and add data to the record from their data sources. The PHR Account Holder may use similar strategies to populate their current state information.
| PH.2#01 | SHALL |
The system SHALL capture and maintain metadata that identifies the author, source, and custodian of the data in the PHR. |
| PH.2#02 | SHALL |
The system SHALL conform to TI.2 (Auditable Records). |
| PH.2#03 | SHOULD |
The system SHOULD provide the ability for the PHR Account Holder to annotate any externally-sourced data with text comments. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Historical health information as well as current health status should be captured and maintained in the health record.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>To obtain historical information to populate the PHR, the PHR Account Holder may use strategies that include entering historical information directly or importing at least part of this data from outside electronic data sources. An outside service such as an employer, insurance plan, provider or care delivery organization may sponsor a particular PHR and add data to the record from their data sources. The PHR Account Holder may use similar strategies to populate their current state information.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL capture and maintain metadata that identifies the author, source, and custodian of the data in the PHR.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to TI.2 (Auditable Records).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the PHR Account Holder to annotate any externally-sourced data with text comments.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2",
"version" : "2.0.1-ballot",
"name" : "PH_2_Manage_Historical_Clinical_Data_and_Current_State_Data",
"title" : "PH.2 Manage Historical Clinical Data and Current State Data (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Historical health information as well as current health status should be captured and maintained in the health record.",
"purpose" : "To obtain historical information to populate the PHR, the PHR Account Holder may use strategies that include entering historical information directly or importing at least part of this data from outside electronic data sources. An outside service such as an employer, insurance plan, provider or care delivery organization may sponsor a particular PHR and add data to the record from their data sources. The PHR Account Holder may use similar strategies to populate their current state information.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2-01",
"label" : "PH.2#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL capture and maintain metadata that identifies the author, source, and custodian of the data in the PHR."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2-02",
"label" : "PH.2#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to TI.2 (Auditable Records)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2-03",
"label" : "PH.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the PHR Account Holder to annotate any externally-sourced data with text comments."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.